Replication-Aware Transactions: How to Roll a Transaction over Failures

The CORBA standard adopted by OMG supports reliability using two orthogonal mechanisms: Replication (by means of FT-CORBA standard) and Transaction (with the aid of OTS standard). Replication represents a rollforward approach in which a failed request is re-directed into another replica that is alive. On the other hand, transaction represents a roll-back approach, in which any failure reverts the system into the last committed state. Current researches show that integrating these two approaches is essential in 3-tier systems, in which the replication protects system processes from failures on the middle tier, whereas transaction concept ensures the data consistency in the data tier. All proposed methods for reconciling these two concepts are unanimous that the transaction approach suffers from poor performance due to the use of two-phase commit protocol. In this paper we introduce RATs (Replication-Aware Transactions) which is a new transaction model based on replicated objects. This kind of transaction can jump over the failures that the replicas come across without rolling the whole transaction back (we call it roll-over). Instead, the failed objects would be removed from the replica list and will be re-created somewhere else if needed. Implementation results of our model show better transaction throughput in comparison with known approaches.